refactor: change HttpClient registration in DI #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use IHttpClientFactory instead of registering a singleton HttpClient.
This way we let the runtime handle the HttpClient lifetime. When using a singleton HttpClient, the DNS can be cached. If for example MangaDex changes the DNS of their domain and MangaMagnet is running for a long period of time, this could be an issue. This is why I changed it to an IHttpClientFactory.